-
Notifications
You must be signed in to change notification settings - Fork 7.6k
Fixes to PAJ7620 driver and code sample #93044
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
cc @paultimke |
LOG_MODULE_REGISTER(paj7620, CONFIG_SENSOR_LOG_LEVEL); | ||
LOG_MODULE_REGISTER(paj7620_trigger, CONFIG_SENSOR_LOG_LEVEL); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason not to use LOG_MODULE_DECLARE
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
duh, of course - Fixed, thanks!
paj7620 log module was being registered twice ; use LOG_MODULE_DECLARE instead in paj7620_trigger.c Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
The current sample was always trying to enable trigger mode in the driver no matter what, causing issues for instances where the sensor simply has no interrupt pin configured in Devicetree. Cleaned things up so that enabling trigger mode is done via the driver's Kconfig option, and cleaned up the Twister testcases accordingly (plus, made sure they are actually built by setting min_ram to a value compatibel with the nucleo_f334r8). README has also been updated to clearly document how to enable either mode. Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
|
Uh oh!
There was an error while loading. Please reload this page.